This page records active development signals, field tests, operator discoveries, Discord experiments, Telegram routing, safety tools, and release-stage decisions around EMA_TEST_LAB.
EMA_TEST_LAB is now in a near-complete pilot release stage. The Windows operator layer, Android ChatGPT bridge, Telegram routing, Discord observation mode, emergency guard utility, and local activation workflow are being prepared as one installable package.
Live EMA operator-layer test:
Discord → Eva → Telegram routing through real desktop interfaces.
In this recording, EMA reads live Discord discussions,
analyzes the atmosphere and conversational signals,
then switches back into Telegram communication mode.
The visible “SWITCH:” line at the beginning is part of the EMA routing contour.
Due to horizontal scrcpy recording mode, the full command
“SWITCH:EMA_DISCORD_LAB” was visually cropped,
although the complete routing command was active internally.
This demo intentionally shows:
— real desktop interaction instead of API-only orchestration
— Discord reading through UI-level operator contours
— explicit switching between communication environments
— human-visible routing state
— AI observations returned through Telegram
— pause / resume operator control
— controlled communication flow
At the current pilot-release stage,
EMA_TEST_LAB is distributed only with Telegram operator workflows enabled.
Discord integration is currently considered experimental
and is being used internally for:
— live AI discussion monitoring
— workflow testing
— routing experiments
— operator-layer research
The long-term EMA architecture is designed to support:
— multiple messengers
— multiple AI assistants
— routed communication contours
— human-supervised operator workflows
Several assistant and routing contours are already functioning internally
through the EMA experimental environment.
Right now the main goal is to evaluate real interest,
operator usability,
workflow stability,
and demand for human-in-the-loop AI systems.
Feedback / contact:
Telegram: @OntoPsyEMALaboratory
Telegram and Discord are controlled through real desktop interfaces. EMA reads, routes, pauses, resumes, and switches between communication contours without relying on a conventional API-first bot architecture.
EMA_GUARD.exe was added as an external emergency stop utility. It allows the operator to terminate EMA_TEST_LAB and scrcpy even if mouse and keyboard automation become locked in a loop.
EMA_DISCORD_LAB can now read live Discord text streams, extract selected message regions, and forward them into the Android ChatGPT contour for interpretation.
The switch loop now detects SWITCH commands from Eva’s response and changes the active peer between Telegram, Discord, and EVA without breaking the main operator cycle.
Discord writing is protected by an explicit marker: TO:SENDDISCORD. Without this marker, EMA remains in read-only mode.
EMA_TEST_LAB does not imitate a simple chatbot. It behaves as an operator layer between human communication platforms and AI reasoning systems.
The goal is not to replace the operator, but to create a controlled semi-autonomous communication contour where every action remains visible, interruptible, and structurally understandable.
Many AI workflows depend on paid API access, platform-specific integrations, or closed bot environments. EMA_TEST_LAB explores another route: controlled interaction through the same interfaces a human operator already uses.
Telegram is used as a direct operator communication layer. Discord is used as a live social observation environment where EMA can read community signals, technical discussions, poetry, feedback threads, and AI culture in motion.